Versions:
npiperelay 0.1.0, released by developer John Starks, is a lightweight, open-source utility designed to bridge the gap between Windows named pipes and the environments where standard command-line tools expect Unix-style sockets or stdin/stdout streams. By re-exposing an existing Windows named pipe as a TCP loopback endpoint, the program lets users invoke familiar utilities such as ssh, socat, netcat, curl, or custom scripts from inside WSL, PowerShell, or CMD without having to rewrite the application or install additional drivers. Typical use cases include forwarding the Docker Engine pipe (`\\.\pipe\docker_engine`) into WSL so that the Linux docker client can build and run containers natively, attaching to Hyper-V or VMMS diagnostic pipes for low-level troubleshooting, or piping Windows service logs directly into grep, awk, or other text-processing filters. The tool runs as a single self-contained executable that listens on a local port, translates the byte stream, and relays it to the specified pipe, thereby avoiding the permission and path-translation issues that often prevent direct interoperability. Because the relay operates entirely in user space, no administrative rights are required beyond those already needed to open the target pipe. npiperelay is catalogued under Developer Tools / System Interoperability and is distributed in both x86-64 and ARM64 builds. Although only one public version (0.1.0) has been published to date, the codebase is version-tagged on GitHub, allowing users to track any future point releases or contribute pull requests for additional features such as TLS wrapping or multiple simultaneous pipe forwarding. The software is available for free on get.nero.com, with downloads provided via trusted Windows package sources (e.g. winget), always delivering the latest version, and supporting batch installation of multiple applications.
Tags: